Release notes
2025r3
Media positions on media in MAM API
The current positions on media describe the positions of managed media, such as server, file share... Additional fields were added to the concept in this version.
Previously, the positions could not be managed using the MAM API.
From this version, several calls for the current media positions have been added:
-
POST /mediaPositions:
Create or update a media position for a specific media. ThemediaIdattribute is mandatory, while the type is only mandatory during creation. -
PUT /mediaPositions/{mediaPositionId}:
Update a media position on a media. -
GET /mediaPositions/{mediaPositionId}:
Retrieve the details of a specific media position. -
DELETE /mediaPositions/{mediaPositionId}:
Delete a media position. -
GET /mediaPositions:
Search for media positions using thetype,subTypeormediaIdas filter parameters. For example:GET /mediaPositions?filter=eq(mediaId,169161)
An example of the response body of the GET /mediaPositions/{mediaPositionId} call:
{
"mediaPositionId": "9501808044",
"type": "FTP",
"subType": "Videos",
"mediaId": "1111456000",
"position": "Files",
"url": "file://FTP/videofolder"
}
The following drop-down calls were added to retrieve the values of the type and subtype attributes:
-
GET /mediaPositionTypes:
Retrieves the values of the MM2ManagedMediaPositionType drop-down list. -
GET /mediaPositionSubtypes:
Retrieves the values of the MM2ManagedMediaPositionSubType drop-down list.
Additionally, the mediaPositions array was added to the existing GET /media/{mediaId} call. It returns the IDs of the positions on a media, so the mediaPosition calls can be used.
An example of the response:
{
"label": "0000000041",
"status": "available",
"library": "The fiery library",
"type": "MAM File",
"networkPath": "/main",
"TCIN": "00:00:00.00",
"TCOUT": "01:30:00.00",
"remarks": null,
"MAMMediaId": "YEUZYEZ76765",
"checksum": "67236IKJDKZ8USD",
"filesize": 350,
...
"linkedMediaAssets": [],
"mediaPositions": [
"9501807846",
"9501808044"
]
}
API developers
The YAML has been updated for these changes. The latest version can be retrieved by using the GET /api call.
Quite a number of changes were done to YAML, so for easier viewing, the YAMLs can be compared here: TextCompare